Memory with output control

ABSTRACT

An apparatus, system, and method for controlling data transfer to an output port of a serial data link interface in a semiconductor memory is disclosed. In one example, a flash memory device may have multiple serial data links, multiple memory banks and control input ports that enable the memory device to transfer the serial data to a serial data output port of the memory device. In another example, a flash memory device may have a single serial data link, a single memory bank, a serial data input port, a control input port for receiving output enable signals. The flash memory devices may be cascaded in a daisy-chain configuration using echo signal lines to serially communicate between memory devices.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/463,339 filed on May 3, 2012, which is a continuation of U.S.application Ser. No. 12/882,931 filed Sep. 15, 2010, now issued as U.S.Pat. No. 8,199,598 on Jun. 12, 2012, which is a continuation of U.S.application Ser. No. 12/275,701 filed Nov. 21, 2008, now U.S. Pat. No.7,826,294, issued on Nov. 2, 2010, which is a continuation of U.S.application Ser. No. 11/583,354 filed on Oct. 19, 2006, now U.S. Pat.No. 7,515,471, issued Apr. 7, 2009, which is a Continuation-in-Part ofU.S. application Ser. No. 11/324,023 filed on Dec. 30, 2005, now U.S.Pat. No. 7,652,922 issued Jan. 26, 2010, which claims the benefit ofU.S. Provisional Application No. 60/722,368 filed on Sep. 30, 2005,entitled “Multiple Independent Serial Link Memory”, which are hereinincorporated by reference. U.S. application Ser. No. 11/583,354 filed onOct. 19, 2006, now U.S. Pat. No. 7,515,471, claims the benefit of U.S.Provisional Application No. 60/847,790 filed on Sep. 27, 2006, and alsoclaims the benefit of U.S. Provisional Application No. 60/722,368 filedon Sep. 30, 2005, entitled “Memory with Output Control”, which areherein incorporated by reference.

FIELD OF THE INVENTION

The invention relates to semiconductor memory devices. Moreparticularly, the invention relates to a memory architecture forimproving the speed and/or capacity of semiconductor Flash memorydevices.

BACKGROUND OF THE INVENTION

Mobile electronic devices, such as digital cameras, portable digitalassistants, portable audio/video players and mobile terminals continueto require mass storage memory, preferably non-volatile memory with everincreasing capacities and speed capabilities. For example, presentlyavailable audio players can have between 256 Mbytes to 40 Gigabytes ofmemory for storing audio/video data. Non-volatile memory such as Flashmemory and hard-disk drives are preferred since data is retained in theabsence of power, thus extending battery life.

Presently, hard disk drives have high densities that can store 20 to 40Gigabytes of data, but are relatively bulky. However, flash memory ispopular because of its high density, non-volatility, and small sizerelative to hard disk drives. Flash memory technology is based on EPROMand EEPROM technologies. The term “flash” was chosen because a largenumber of memory cells could be erased at one time as distinguished fromEEPROMs, where each byte was erased individually. The advent ofmulti-level cells (MLC) further increases Flash memory density relativeto single level cells. Those of skill in the art will understand thatFlash memory can be configured as NOR Flash or NAND Flash, with NANDFlash having higher density per given are due to its more compact memoryarray structure. For the purpose of further discussion, references toFlash memory should be understood as being either NOR or NAND or othertype Flash memory.

While existing Flash memory modules operate at speeds sufficient formany current consumer electronic devices, such memory modules likelywill not be adequate for use in further devices where high data ratesare desired. For example, a mobile multimedia device that records highdefinition moving pictures is likely to require a memory module with aprogramming throughput of at least 10 MB/s, which is not obtainable withcurrent Flash memory technology with typical programming data rates of 7MB/s. Multi-level cell Flash has a much slower rate of 1.5 MB/s due tothe multi-step programming sequence required to program the cells

Programming and read throughput for Flash memory can be directlyincreased by increasing the operating frequency of the Flash memory. Forexample, the present operating frequency of about 20-30 MHz can beincreased by an order of magnitude to about 200 MHz. While this solutionappears to be straightforward, there is a significant problem withsignal quality at such high frequencies, which sets a practicallimitation on the operating frequency of the Flash memory. Inparticular, the Flash memory communicates with other components using aset of parallel input/output (I/O) pins, numbering 8 or 16 depending onthe desired configuration, which receive command instructions, receiveinput data and provide output data. This is commonly known as a parallelinterface. High speed operating will cause well known communicationdegrading effects such as cross-talk, signal skew and signalattenuation, for example, which degrades signal quality.

Such parallel interfaces use a large number of pins to read and writedata. As the number of input pins and wires increases, so do a number ofundesired effects. These effects include inter-symbol interferences,signal skew and cross talk. Inter-symbol interference results from theattenuation of signals traveling along a wire and reflections causedwhen multiple elements are connected to the wire. Signal skew occurswhen signals travel along wires having different lengths and/orcharacteristics and arrive at an end point at different times. Crosstalk refers to the unwanted coupling of signals on wires that are inclose proximity. Cross talk becomes more of a problem as the operatingspeed of the memory device increases.

Therefore, there is a need in the art for memory modules, for use inmobile electronic devices, and solid-state drive applications that haveincreased memory capacities and/or operating speeds while minimizing thenumber input pins and wires required to access the memory modules.

SUMMARY OF THE INVENTION

The following represents a simplified summary of some embodiments of theinvention in order to provide a basic understanding of various aspectsof the invention. This summary is not an extensive overview of theinvention. It is not intended to identify key or critical elements ofthe invention or to delineate the scope of the invention. Its solepurpose is to present some embodiments of the invention in simplifiedform as a prelude to the more detailed description that is presentedbelow.

In accordance with an embodiment of the present invention, asemiconductor memory device includes a memory, a serial data link thattransfers serial input data to the memory, and an input control signal.Control circuitry controls data transfer between the serial data linkinterface and the memory. Consistent with the principle of the presentinvention, the memory may be a single memory bank or multiple memorybanks. The serial data link interface may convert serial input data intoparallel data to be transferred to the memory bank. Additionally, theserial link interface may convert parallel data from the memory bank toserial output data. Various other aspects of the invention are alsodisclosed throughout the specification.

According to principles of the present invention, a flash memory systemmay have plurality of serially connected flash memory devices. The flashmemory devices in the system include a serial input data port, a serialdata output port, a plurality of control input ports, and a plurality ofcontrol output ports. The flash memory devices are configured to receiveserial input data and control signals from an external source and toprovide data and control signals to an external device. The externalsource and external device may be other flash memory devices within thesystem. In some embodiments of the present invention, each of the flashmemory devices may include a unique device identifier. The devices maybe configured parse a target device information field in serial inputdata to correlate target device information with the unique deviceidentification number of the device to determine whether the device isthe target device. The device may parse the target device informationfield prior to processing any additional input data received. If thememory device is not the target device, it may ignore the serial inputdata, thus saving additional processing time and resources.

According to embodiments of the present invention, a memory device andmethod fully serializes a single set of serial input and output pinswhich are SIP (Serial Input Port) and SOP (Serial Output Port) alongwith two control signals, IPE (Input Port Enable) and OPE (Output PortEnable), for the enabling/disabling of input/output ports respectively.This provides a memory controller maximum flexibility of datacommunication. The memory device of the present invention receives aninformation signal stream through its SIP port only when IPE stays in a‘High’ logic state, and also the device transmits the output data signalstream through its SOP port only when OPE stays in a ‘High’ logic state.When IPE goes to ‘High’, referenced at rising edges of free-runningSerial Clock signal (SCLK), the SIP port starts to receive consecutiveserial input stream bytes which are device address byte, command byte,column address bytes, row address bytes and/or input data bytes inpredetermined number of clock cycles for each operation cases. If IPEgoes to a ‘Low’ state, the SIP port stops receiving input signalstreaming bytes. When OPE signal goes to a ‘High’ state, the SOP portstarts to output data referenced at rising edges of free-running SerialClock signal (SCLK). If OPE goes to a ‘Low’ state, the SOP stopsoutputting data. Therefore, the memory controller can have moreflexibility to control communication between memory devices andcontroller itself.

In addition, when devices are serially cascaded in a system they mayfurther comprise output control ports that “echo” the received IPE andOPE signals to external devices. This allows the system to havepoint-to-point connected signal ports (e.g., SIP/SOP, IPE/IPEQ,OPE/OPEQ, SCLKI/SCLKO) to form a daisy-chain cascading scheme (versusbroadcasting/multi-drop cascading scheme). These systems may use theunique device identification and target device selection address scheme,rather than using limited hardware physical device select pins, so thatthe whole system can be easily expanded as many as possible in terms ofmemory density without sacrificing system's overall performance.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIGS. 1A, 1B, 1C illustrate high level diagrams showing illustrativememory devices that allow for concurrent operations, in accordance withvarious aspects of the invention.

FIG. 2A is a high-level block diagram of an illustrative memory devicein accordance with aspects of the invention.

FIG. 2B is a schematic of a serial data link shown in FIG. 2A, accordingto an embodiment of the present invention.

FIG. 2C is a schematic of an input serial to parallel register blockshown in FIG. 2A, according to an embodiment of the present invention.

FIG. 2D is a schematic of a path switch circuit shown in FIG. 2A,according to an embodiment of the present invention.

FIG. 2E is a schematic of an output parallel to serial register blockshown in FIG. 2A, according to an embodiment of the present invention.

FIGS. 3A, 4, 5A, 6A, and 7 illustrate timing diagrams for memoryoperations performed by a memory device in accordance with variousaspects of the invention. FIGS. 3B, 5B, and 6B are flowchartsillustrating the memory operations of FIGS. 3A, 5A, and 6A,respectively, in a device in accordance with various aspects of theinvention.

FIGS. 8A, 8B, and 8C illustrate timing diagrams for concurrent memoryoperations performed in a memory device in accordance with variousaspects of the invention.

FIGS. 9 and 10 are flowcharts diagramming a method of controlling datatransfer between a plurality of serial data link interfaces and aplurality of memory banks in accordance with various aspects of theinvention.

FIG. 11 illustrates a block diagram of the pin-out configuration of amemory device in device in accordance with various aspects of theinvention.

FIG. 12 illustrates timing diagrams for a memory operations performed ina memory device equipped with various aspects of the virtual multiplelink feature in accordance with the invention.

FIG. 13A depicts a high-level block diagram of a cascaded configurationof numerous memory devices in accordance with various aspects of theinvention.

FIG. 13B depicts a high-level block diagram of an alternate cascadedconfiguration of numerous memory devices in accordance with variousaspects of the invention.

FIG. 14 illustrates a simplified timing diagram for a memory operationperformed on a memory device in a cascaded configuration in accordancewith aspects of the invention.

FIG. 15A is a high-level block diagram of an illustrative memory devicein accordance with aspects of the invention.

FIG. 15B is a more detailed block diagram of a serial link interfacethat may be used in the memory device illustrated in FIG. 15A.

FIGS. 16A and 16B illustrate timing diagrams for input latch timing andinput sequence timing byte mode, respectively.

FIGS. 17A and 17B illustrate timing diagrams for output latch timing andoutput sequence timing byte mode, respectively.

DETAILED DESCRIPTION

A serial data interface for a semiconductor memory is disclosed. Theserial data interface can include one or more serial data links incommunication with centralized control logic, where each serial datalink can receive commands and data serially, and can provide output dataserially. Each serial data link can access any memory bank in the memoryfor programming and reading of data. At least one advantage of a serialinterface is a low-pin-count device with a standard pin-out that is thesame from one density to another, thus, allowing compatible futureupgrades to higher densities without board redesign.

FIGS. 1A and 1B are high level diagrams showing illustrative memorydevices that support concurrent operations, in accordance with variousaspects of the invention. FIG. 1A shows a memory device having multipleserial data link interfaces 102 and 104 and multiple memory banks 106and 108. The presently shown arrangement is referred to herein as a dualport configuration. Each serial data link interface has an associatedinput/output pin and data input and data output circuitry, which will bedescribed in further detail with respect to FIG. 2A. Data transferredthrough a serial data link interface passes through in a serial fashion(e.g., as a single-bit-wide stream of data.) Each of the data linkinterfaces 102 and 104 in the memory device are independent and cantransfer data to and from any of the memory banks 106 and 108. Forexample, serial data link 102 can transfer data to and from memory bank106 or memory bank 108. Similarly, serial data link 104 can transferdata to and from memory bank 106 and memory bank 108. Since the twoserial data link interfaces shown are independent, they can concurrentlytransfer data to and from separate memory banks. Link, as used herein,refers to the circuitry that provides a path for, and controls thetransfer of, data to and from one or more memory banks. A control module110 is configurable with commands to control the exchange of databetween each serial data link interface 102 and 104 and each memory bank106 and 108. For example, control module 110 can be configured to allowserial data link interface 102 to read data from memory bank 106 at thesame time that serial data link interface 104 is writing data to memorybank 108. This feature provides enhanced flexibility for system designand enhanced device utilization (e.g., bus utilization and coreutilization). As will be shown later, control module 110 can includecontrol circuits, registers and switch circuits.

FIG. 1B shows an embodiment in which a single serial data link interface120 is linked to multiple memory banks 122 and 124 via a control module126. This presently shown arrangement is referred to herein as a singleport configuration, and utilizes less memory device input/output pinsthan the dual port configuration shown in FIG. 1A. Control module 126 isconfigured to perform or execute two operating processes or threads, sothat serial data link interface 120 can exchange data with memory banks122 and 124 in a pipelined fashion. For example, while data is beingwritten into memory bank 122, data link interface 120 can be readingdata out of memory bank 124. In accordance with various aspects of theinvention and as will be described in further detail below, the memorydevice emulates multiple link operations using a single linkconfiguration with illustrated in FIG. 1B. Using this single link inconjunction with multiple banks configuration, also referred to hereinas a virtual multiple link, any available bank can be accessed while theother bank may be in a busy state. As a result, the memory device canachieve enhanced utilization of a single link configuration by accessingthe other available bank through link arbitration circuitry.

The memory devices shown in FIGS. 1A and 1B include two memory banks forillustration purposes only. One skilled in the art will appreciate thatseveral aspects of the invention disclosed herein are scalable and allowfor the use of multiple memory banks and multiple serial data linkinterfaces. A single memory device may include, for example, 2, 4, ormore memory banks. FIG. 1C shows an embodiment in which four independentserial data links 132, 134, 136 and 138 are configured to exchange datawith four memory banks 140, 142, 144 and 146 under the control of acontrol module 150. With a virtual multiple link configuration only onelink is necessary, so the remaining links (e.g., in FIG. 1A dual link orFIG. 1C quad link pinout configurations) are not used and may beconsidered as NC (i.e., No Connection). At least one advantage of aserial data link interface compared to a conventional parallel interfacestructure, is the reduced number of pins on the memory device while linkflexibility and large density are maintained. For example, while aconventional flash memory device may require 48 pins over multiple sidesof a package, a memory device in accordance with aspects of theinvention may utilize fewer pins (e.g., 11 pins) on a single side of astandard package 1100, as illustrated in FIG. 11. Alternatively, adifferent and smaller type of package can be used instead, since thereare less internal bond pads that are required.

FIG. 2A illustrates a more detailed schematic diagram of the memorydevice shown in FIG. 1A, according to one embodiment of the presentinvention. The architecture of each memory bank in the memory device 200may be the same or similar to a NAND Flash memory core architecture.FIG. 2A illustrates those circuits which are relevant to the invention,and intentionally omits certain circuit blocks to simplify FIG. 2A. Forexample, memory device 200 implemented with a Flash memory corearchitecture will include high voltage generator circuits that arenecessary for programming and erasing the memory cells. Corearchitecture (or core circuitry), as used herein, refers to circuitryincluding memory cell array and associated access circuitry such asdecoding and data transfer circuitry. As standard memory architecturesare well known, so are the native operations associated with theselected architecture, which should be understood by any person skilledin the art. It should be further understood by those of skill in the artthat any known non-volatile or volatile memory architecture can be usedin alternative embodiments of the present invention.

Memory device 200 includes a multiplicity of identical memory banks withtheir respective data, control and addressing circuits, such as memorybank A 202 and memory bank B 204, an address and data path switchcircuit 206 connected to both memory banks 202 and 204, and identicalinterface circuits 205 and 207, associated with each memory bank forproviding data to and for receiving data from the switch circuit 206.Memory banks 202 and 204 are preferably non-volatile memory, such asFlash memory, for example. Logically, the signals received and providedby memory bank 202 are designated with the letter “A”, while the signalsreceived and provided by memory bank 204 are designated with the letter“B”. Similarly, the signals received and provided by interface circuit205 are designated with the number “0”, while the signals received andprovided by interface circuit 207 are designated with the number “1”.Each interface circuit 205/207 receives access data in a serial datastream, where the access data can include a command, address informationand input data for programming operations, for example. In a readoperation, the interface circuit will provide output data as a serialdata stream in response to a read command and address data. The memorydevice 200 further includes global circuits, such as a control interface208 and status/ID register circuit 210, which provide global signalssuch as clock signal sclki and reset to the circuits of both memorybanks 202 and 204 and the respective interface circuits 205 and 207. Afurther discussion of the aforementioned circuits now follows.

Memory bank 202 includes well known memory peripheral circuits such assense amplifier and page buffer circuit block 212 for providing outputdata DOUT_A and for receiving input program data DIN_A, and row decoderblock 214. Those of skill in the art will understand that block 212 willalso include column decoder circuits. A control and predecoder circuitblock 216 receives address signals and control signals via signal lineADDR_A, and provides predecoded address signals to the row decoders 214and the sense amplifier and page buffer circuit block 212.

The peripheral circuits for memory bank 204 are identical to thosepreviously described for memory bank 202. The circuits of memory bank Binclude a sense amplifier and page buffer circuit block 218 forproviding output data DOUT_B and for receiving input program data DIN_B,a row decoder block 220, and a control and predecoder circuit block 222.Control and predecoder circuit block 222 receives address signals andcontrol signals via signal line ADDR_B, and provides predecoded addresssignals to the row decoders 220 and the sense amplifier and page buffercircuit block 222. Each memory bank and its corresponding peripheralcircuits can be configured with well known architectures.

In general operation, each memory bank is responsive to a specificcommand and address, and if necessary, input data. For example, memorybank 202 will provide output data DOUT_A in response to a read commandand a read address, and can program input data in response to a programcommand and a program address. Each memory bank can be responsive toother commands such as an erase command, for example.

In the presently shown embodiment, path switch 206 is a dual portcircuit which can operate in one of two modes for passing signalsbetween the memory banks 202 and 204, and the interface circuits 205 and207. First is a direct transfer mode where the signals of memory bank202 and interface circuit 205 are passed to each other. Concurrently,the signals of memory bank 204 and interface circuit 207 are passed toeach other in the direct transfer mode. Second is a cross-transfer modewhere the signals of memory bank 202 and interface circuit 207 arepassed to each other. At the same time, the signals of memory bank 204and interface circuit 205 are passed to each other. A single portconfiguration of path switch 206 will be discussed later.

As previously mentioned, interface circuits 205 and 207 receive andprovide data as serial data streams. This is for reducing the pin-outrequirements of the chip as well as to increase the overall signalthroughput at high operating frequencies. Since the circuits of memorybanks 202 and 204 are typically configured for parallel address anddata, converting circuits are required.

Interface circuit 205 includes a serial data link 230, input serial toparallel register block 232, and output parallel to serial registerblock 234. Serial data link 230 receives serial input data SIP0, aninput enable signal IPE0 and an output enable signal OPE0, and providesserial output data SOP0, input enable echo signal IPEQ0 and outputenable echo signal OPEQ0. Signal SIP0 (and SIP1) is a serial data streamwhich can each include address, command and input data. Serial data link230 provides buffered serial input data SER_IN0 corresponding to SIP0and receives serial output data SER_OUT0 from output parallel to serialregister block 234. The input serial-to-parallel register block 232receives SER_IN0 and converts it into a parallel set of signals PAR_IN0.The output parallel-to-serial register block 234 receives a parallel setof output data PAR_OUT0 and converts it into the serial output dataSER_OUT0, which is subsequently provided as data stream SOP0. Outputparallel-to-serial register block 234 can also receive data fromstatus/ID register circuit 210 for outputting the data stored thereininstead of the PAR_OUT0 data. Further details of this particular featurewill be discussed later. Furthermore, serial data link 230 is configuredto accommodate daisy chain cascading of the control signals and datasignals with another memory device 200.

Serial interface circuit 207 is identically configured to interfacecircuit 205, and includes a serial data link 236, inputserial-to-parallel register block 240, and output parallel-to-serialregister block 238. Serial data link 236 receives serial input dataSIP1, an input enable signal IPE1 and an output enable signal OPE1, andprovides serial output data SOP1, input enable echo signal IPEQ1 andoutput enable echo signal OPEQ1. Serial data link 236 provides bufferedserial input data SER_IN1 corresponding to SIP1 and receives serialoutput data SER OUT1 from output parallel-to-serial register block 238.The input serial-to-parallel register block 238 receives SER_IN1 andconverts it into a parallel set of signals PAR_IN1. The outputparallel-to-serial register block 240 receives a parallel set of outputdata PAR_OU 1 and converts it into the serial output data SER_OUT1,which is subsequently provided as data stream SOP1. Output parallel toserial register block 240 can also receive data from status/ID registercircuit 210 for outputting the data stored therein instead of thePAR_OUT1 data. As with serial data link 230, serial data link 236 isconfigured to accommodate daisy chain cascading of the control signalsand data signals with another memory device 200.

Control interface 208 includes standard input buffer circuits, andgenerates internal chip select signal chip_sel, internal clock signalsclki, and internal reset signal reset, corresponding to CS#, SCLK andRST# respectively. While signal chip_sel is used primarily by serialdata links 230 and 236, reset and sclki are used by many of the circuitsthroughout memory device 200.

FIG. 2B is a schematic of serial data link 230, according to anembodiment of the invention. Serial data link 230 includes input buffers242 for receiving input signals OPE0, IPE0 and SIP0, output drivers 244for driving signals SOP0, IPEQ0 and OPEQ0, flip-flop circuits 246 forclocking out signals out_en0 and in_en0, inverter 248 and multiplexor(MUX) 250. The input buffers for signals OPE0 and SIP0 are enabled inresponse to chip_sel, and the output driver for signal SOP0 is enabledin response to an inverted chip_sel via inverter 248. Signal out-en0enables an output buffer, which is shown later in FIG. 2E and providessignal SER_OUT0. Signal in_en0 enables the input serial to parallelregister block 232 to latch SER_IN0 data. Signals in_en0, out_en0 andSER_IN0.

Serial data link 230 includes circuits to enable daisy chain cascadingof the memory device 200 with another memory device. More specifically,the serial input data stream SIP0, and enable signals OPE0 and IPE0 canbe passed through to the corresponding pins of another memory devicethrough serial data link 230. SER_IN0 is received by AND logic gate 252and passed to its corresponding flip-flop 246 when in_en0 is at theactive high logic level. Simultaneously, in_en0 at the active high logiclevel will control MUX 250 to pass Si_next0 to output driver 244.Similarly, IPE0 and OPE0 can be clocked out to IPEQ0 and OPEQ0 throughrespective flip-flops 246. While serial data link 230 has beendescribed, it is noted that serial data link 236 includes the samecomponents, which are interconnected in the same way as shown for serialdata link 230 in FIG. 2B.

FIG. 2C is a schematic of the input serial to parallel register block232. This block receives the clock signal sclki, the enable signalin_en0 and the input data stream SER_IN0, and converts SER_IN0 intoparallel groups of data. In particular, SER_IN0 can be converted toprovide a command CMD_0, a column address C_ADD0, a row address R_ADD0and input data DATA_IN0. The presently disclosed embodiment of theinvention preferably operates at a high frequency, such as at 200 MHzfor example. At this speed, the serial input data stream can be receivedat a rate faster than the received command can be decoded. It is forthis reason that the serial input data stream is initially buffered in aset of registers. It should be understood that the presently shownschematic also applies to input serial to parallel register block 240,where the only difference lies in the designator of the signal names.

The input serial-to-parallel register block 232 includes an inputcontroller 254 for receiving in_en0 and sclki, a command register 256, atemporary register 258, and a serial data register 260. Since the datastructure of the serial input data stream is predetermined, specificnumbers of bits of the input data stream can be distributed to theaforementioned registers. For example, the bits corresponding to acommand can be stored in the command register 256, the bitscorresponding to row and column addresses can be stored in the temporaryregister 258, and the bits corresponding to input data can be stored inthe serial data register 260. The distribution of the bits of the serialinput data stream can be controlled by input controller 254, which vaninclude counters for generating the appropriate register enablingcontrol signals after each predetermined number of bits have beenreceived. In other words, each of the three registers can besequentially enabled to receive and store bits of data of the serialinput data stream in accordance with the predetermined data structure ofthe serial input data stream.

A command interpreter 262 receives a command signal in parallel fromcommand register 256, and generates a decoded command CMD_0. Commandinterpreter 262 is a standard circuit implemented with interconnectedlogic gates or firmware, for decoding the received commands. As shown inFIG. 2C, CMD_0 can include signals cmd_status and cmd_id. A switchcontroller 264 receives one or more signals from CMD_0 to control asimple switch circuit 266. Switch circuit 266 receives all the datastored in the temporary register 258 in parallel, and loads one or bothof column address register 268 and row/bank register 270 with data inaccordance with the decoded command CMD_0. This decoding is preferablydone because the temporary register may not always include both columnand row/bank address data. For example, a serial input data streamhaving a block erase command will only use a row address, in which caseonly the relevant bits stored in the temporary register 258 are loadedinto row/bank register 270. The column address register 268 providesparallel signal C-ADD0, the row/bank address register 270 providesparallel signal R_ADD0, and data register 272 provides parallel signalDATA_IN0, for programming operations. Collectively, CMD_0, C_ADD0,R_ADD0) and Data_IN0 (optional), form the parallel signal PAR_IN0. Bitwidths for each of the parallel signals have not been specified, as thedesired width is a design parameter which can be customized, or tailoredto adhere to a particular standard.

Examples of some of the operations of the memory device 200 for a Flashcore architecture implementation are shown in Table 1 below. Table 1lists possible OP (operation) codes for CMD_0 and corresponding statesof the column address (C_ADD0), row/bank address (R_ADD0), and the inputdata (DATA_IN0).

TABLE 1 Command Set OP Column Row/Bank Input Data Code Address Address(1 Byte to Operation (1 Byte) (2 Bytes) (3 Bytes) 2112 Bytes) Page Read00h Valid Valid — Random Data Read 05h Valid — — Page Read for Copy 35h— Valid — Target Address 8Fh — Valid — Input for Copy Serial Data Input80h Valid Valid Valid Random Data Input 85h Valid — Valid Page Program10h — — — Block Erase 60h — Valid — Read Status 70h — — — Read ID 90h —— — Write Configuration A0h — — Valid (1 Byte) Register Write DN (DeviceB0h — — — Name) Entry Reset FFh — — — Bank Select 20h — Valid (Bank) —

Furthermore, Table 2 shows the preferred input sequence of the inputdata stream. The commands, addresses, and data are serially shifted inand out of the memory device 200, starting with the most significantbit. Command sequences start with a one-byte command code (“cmd” inTable 2). Depending on the command, the one-byte command code may befollowed by column address bytes (“ca” in Table 2), row address bytes(“ra” in Table 2), bank address bytes (“ba” in Table 2), data bytes(“data” in Table 2), and/or a combination or none.

TABLE 2 Input Sequence in Byte Mode 1^(st) 2^(nd) 3^(rd) 4^(th) 5^(th)6^(th) 7^(th) 2115^(th) 2118^(th) Operation Byte Byte Byte Byte ByteByte Byte ...Byte ...Byte Page Read cmd ca Ca ba/ra ra ra — — — — —Random Data Read cmd ca Ca — — — — — — — — Page Read for Copy cmd ba/raRa ra — — — — — — — Target Address Input cmd ba/ra Ra ra — — — — — — —for Copy Serial Data Input cmd ca Ca ba/ra ra ra data ...data ...dataRandom Data Input cmd ca Ca data data data data ...data — — Page Programcmd — — — — — — — — — — Block Erase cmd ba/ra Ra ra — — — — — — — ReadStatus cmd — — — — — — — — — — Read ID cmd — — — — — — — — — — WriteConfiguration cmd data — — — — — — — — — Register Write DN Entry cmd — —— — — — — — — — Reset cmd — — — — — — — — — — Bank Select cmb ba — — — —— — — — —

FIG. 2D is a schematic of path switch 206 shown in FIG. 2A. Switch 206is logically divided into two switch sub-circuits 274 and 276, which areidentically configured. Switch sub-circuit 274 includes four inputmultiplexors 278 that selectively pass the commands, addresses and inputdata of either interface circuit 205 or interface circuit 207 to thecircuits of memory bank 202. These signals have been previously groupedin FIG. 2C as PAR_IN0 by example. Switch sub-circuit 274 includes oneoutput multiplexor 280 for selectively passing the output data fromeither memory bank 202 or memory bank 204 to interface circuit 205.Switch sub-circuit 276 includes four input multiplexors (not shown) thatselectively pass the commands, addresses and input data of eitherinterface circuit 205 or interface circuit 207 to the circuits of memorybank 204. Switch sub-circuit 276 includes one output multiplexor (notshown) for selectively passing the output data from either memory bank202 or memory bank 204 to interface circuit 207.

Both switch sub-circuits 274 and 276 can simultaneously operate in thedirect transfer mode or the cross-transfer mode, depending on the stateof switch control signal SW_CONT. Path switch circuit 206 is presentlyshown in a dual port configuration, meaning that both memory banks 202and 204 can be simultaneously accessed through either interface circuits205 and 207.

According to another embodiment of the present invention, as previouslyillustrated in FIG. 1B, path switch 206 can operate in a single portmode in which only one of interface circuits 205 and 207 is active. Thisconfiguration can further reduce the pin-out area requirements of thememory device 200 since the input/output pads associated with the unusedinterface circuit are no longer required. In the single portconfiguration, switch sub-circuits 274 and 276 are set to operate in thedirect transfer mode only, with the exception of the respective outputmultiplexors 280 which can remain responsive to the SW_CONT selectionsignal.

In a single port embodiment where only interface circuit 205 is active,a supplemental path switch (not shown) is included in the input parallelto serial register block 232 (or block 234), for selectively passing thedata from the outputs of switch 266 and serial data register 260 to thecorresponding column, row/bank and data registers of either input serialto parallel register block 232 or 240. Effectively, the supplementalpath switch can be similar to switch 206. Hence, the column, row/bankand data registers of both input serial to parallel register blocks 232and 240 can be loaded with data for alternate memory bank accesses, orfor substantially concurrent accesses.

FIG. 2E is a schematic of output parallel-serial register block 234. Itis noted that output parallel-to-serial register block 238 isidentically configured. Output parallel-to-serial register block 234provides either data accessed from the memory bank, or status datapreviously stored in registers. More specifically, the user or systemcan request a status of either serial data links 230 or 236. A value of‘1’ in a designated bit location (e.g., bit 4) in the outputted statusdata can indicate that the particular serial data link interface isbusy. The fixed data can further include chip identification data, whichwith the status data, can both be pre-loaded with default states uponpower up of the memory device 200. The status data can be configured tohave any preselected bit pattern that is recognizable by the system.Although not shown, FIG. 2E can include additional control circuitry forupdating one or more bits stored in register 284, based on one or morepredetermined conditions. For example, one or more status bits can bechanged based on a count of elapsed clock cycles, or based on acombination of one or more flag signals received from various circuitblocks of memory device 200.

Output parallel to serial register block 234 includes a firstparallel-to-serial register 282 for receiving output data PAR_OUT0 frompath switch 206, a second parallel-to-serial register 284 for receivingfixed data from a multiplexor 286. Multiplexor 286 selectively passesone of the status data stored in status register 288 or chipidentification data stored in ID register 290 in response to signalcmd_id. An output multiplexor 292 passes the data from either the firstparallel-to-serial register 282 or the second parallel-to-serialregister 284 in response to either cmd_id or cmd_status being active,via OR gate 294. Finally, a serial output control circuit 296 enabled byout-en0 provides SER_OUT0.

One skilled in the art will appreciate that the size and location of thestatus indicator may be altered in accordance with various aspects ofthe invention. For example, the serial data link interface statusindicator may be jointed with other types of status indicator (e.g.,memory bank status indicator) and/or physically located outside theregister block (e.g., in the link arbitration module or in the controlmodule 238). In other example, the serial data link interface statusindicator is a one-bit register.

FIG. 15A is a high-level block diagram of an illustrative memory devicein accordance with aspects of the invention. The architecture of thememory bank 202 in the memory device 1500 may be the same or similar toa NAND Flash memory core architecture. Certain circuit blocks areomitted to simplify FIG. 15A. For example, memory device 1500implemented with a Flash memory core architecture will include highvoltage generator circuits that are necessary for programming anderasing the memory cells. Core architecture (or core circuitry), as usedherein, refers to circuitry including memory cell array and associatedaccess circuitry such as decoding and data transfer circuitry. Asstandard memory architectures are well known, so are the nativeoperations associated with the selected architecture, which should beunderstood by any person skilled in the art. It should be furtherunderstood by those of skill in the art that any known non-volatile orvolatile memory architecture can be used in alternative embodiments ofthe present invention.

The memory device 1500 includes a memory bank 202, a serial data linkinterface 205 that transfers serial input data to the memory bank.Memory bank 202 includes well known memory peripheral circuits such assense amplifier and page buffer circuit block 212 for providing outputdata DOUT and for receiving input program data DIN, and row decoderblock 214. Those of skill in the art will understand that block 212 willalso include column decoder circuits. As shown in FIG. 15A, the seriallink interface 205 includes a serial input port (SIP), a serial outputport (SOP), an input enable control port (IPE), an output enable controlport (OPE), an input enable echo control port (IPEQ), and an outputenable echo control port (OPEQ). Those of ordinary skill in the art willunderstand that serial link interface 205 may further include otherdevice ports such as a chip select (CS#) pin, a clock signal input(SCLK), or a reset select (RST#) pin.

FIG. 15B is a more detailed block diagram of a serial link interfacethat may be used in the memory device illustrated in FIG. 15A. Similarto the memory device 200 of FIG. 2A, interface circuit 205 includes aserial data link 230, input serial to parallel register block 232, andoutput parallel to serial register block 234. Serial data link interface230 receives serial input data SIP, an input enable signal IPE and anoutput enable signal OPE, and provides serial output data SOP, inputenable echo signal IPEQ and output enable echo signal OPEQ. Signal SIPis a serial data stream which can each include address, command andinput data. Serial data link 230 provides buffered serial input dataSER_in corresponding to SIP and receives serial output data SER_out fromthe output of parallel-to-serial register block 234. The input ofserial-to-parallel register block 232 receives SER_in and converts itinto a parallel set of signals PAR_in. The output of parallel-to-serialregister block 234 receives a parallel set of output data PAR_in andconverts it into the serial output data SER_out, which is subsequentlyprovided as data stream SOP. Furthermore, the input enable signal IPE,an output enable signal OPE, input enable echo signal IPEQ and outputenable echo signal OPEQ are used to configure serial data link 230 toaccommodate daisy chain cascading of the control signals and datasignals with another memory device 1500. A control module 208 controlsdata transfer between the serial data link interface and the memorybank.

FIGS. 3A, 4, 5A, 6A, and 7 illustrate example timing diagrams for somememory operations performed by memory device 200 in accordance withvarious aspects of the invention. Some memory commands performed by thememory device 200 include, but are not limited to, page read, randomdata read, page read for copy, target address input for copy, serialdata input, random data input, page program, block erase, read status,read ID, write configuration register, write device name entry, reset,and/or bank select. The following discussion of the timing diagrams ismade with reference to the previously described embodiments of thememory device 200 shown in the previous figures, and Tables 1 and 2.

In the example depicted in the timing diagram of FIG. 3A, a “page read”memory command 314 is received at serial data link 230 of a memorydevice 200 in accordance with the invention. Moreover, FIG. 3B shows asimplified flowchart paralleling the operation of the “page read” memorycommand 314 in the timing diagram of FIG. 3A. As a practical matter, thesteps illustrated in FIG. 3B will be discussed in conjunction with thetiming diagram of FIG. 3A. By way of example, in step 324, a “page read”memory command 314 is read in at serial data link 230 of the memorydevice 200.

The incoming data stream in this example is a six-byte serial datastream (i.e., serial input data) including command data (in the firstbyte), column address data (in the second and third bytes), and row andbank address data (in the fourth, fifth, and sixth bytes). As discussedlater, with respect to target device addressing, the serial data streammay include an additional byte that identifies a target device address(‘tda’) and that precedes the command data in the bit stream. The bankaddress can be used to determine access to either bank 202 or 204 viapatch switch 206. One skilled in the art will understand that differentmemory commands may have a different data stream. For example, a “randomdata read” memory command has a predetermined data stream of only threebytes: command data (in the first byte) and column address data (in thesecond and third bytes). In the latter example, the address field of theserial input data only contained column address data and was two byteslong. Meanwhile, in the former example, the address field was five byteslong. One skilled in the art will appreciate after review of theentirety disclosed herein that numerous memory commands andpredetermined data steams are apparent in accordance with variousaspects of the invention.

Continuing with the example involving the “page read” memory command asillustrated in FIG. 3 a, while the chip select (CS#) signal 302 is setlow and in response to the input port enable (IPEX) signal 306 set high,the serial input (SIPx) port 308 is sampled on the first rising edge ofthe serial clock (SCLK) signal 304 (where ‘x’ acts as a placeholderrepresenting the link interface number, e.g., link 0 interface 232 orlink 1 interface 234). The data read out (in step 328) is a data streamcorresponding to a “page read” memory command 314. The CS# signal 302 isan input into the memory device 200 and may be used, among other things,to indicate whether the memory device 200 is active (e.g., when CS# islow). The IPEx signal 306 indicates whether an incoming data stream willbe received at a particular link interface (e.g., when IPEx is high) orwhether a particular link interface will ignore the incoming data stream(e.g., when IPEx is low). The incoming data stream is received at thememory device at the SIPx 308 of a link interface. Finally, the systemclock (SCLK) signal 304 is an input into the memory device 200 and isused to synchronize the various operations performed by the numerouscircuits of the memory device 200. It will be apparent to one skilled inthe art that a memory device in accordance with various aspects of theinvention may be synchronized with such a clock signal (e.g., operationsand data transfers occur at the rising and/or falling edge of the clocksignal) or may be asynchronous (i.e., not synchronous). Alternatively,in a double data rate (DDR) implementation, both the rising and fallingedges of the SCLK clock signal may be used to latch information. In theexample of FIG. 3A, however, input data is latched on the falling edgeof SCLK and output data 322 appears on the serial output pin 312 SOPxafter the rising edge of SCLK.

The status of the “page read” can be checked on the SOPx pin 312 asshown in FIG. 3A, whereby a “bank busy” result will be provided on SOPxuntil a time 318 when a “ready” indication will appear, and the outputdata will shortly appear during a time 322. It should be noted thatalthough FIG. 3A illustrates a “page read” with subsequent “readstatus”, a “page read” without a “read status” is also contemplated inaccordance with aspect of the invention. In that embodiment, no datawould be provided on the SOPx pin until output data would be ready.

The command data sampled by SIPx is written to the appropriate register(e.g., command register 256) in FIG. 2C. At least one benefit to theoption of designing the incoming data stream such that the first byte iscommand data is that the data can be transferred to the command registerwithout additional processing. Subsequent bytes in the data stream maybe address data and/or input data according to the type of memorycommand. One skilled in the art will appreciate that the set of memorycommands recognized by a memory device in accordance with variousaspects of the invention may be defined by word-basis (i.e., 16 bits) orany I/O width. In FIG. 3A, the command data (i.e., 00 h corresponding to“page read” 314) is followed by five bytes of address data: two bytes ofcolumn address data and three bytes of row/bank address data. Theaddress data is written to an address register 258 in FIG. 2C. Theaddress data is used to locate the data stored in the memory bank 202that is to be read. The pre-decoder circuit 216, column decoder incircuit 212, and row decoder 214, are utilized during this process toselect data to be read. For example, the pre-decoder module 214, is usedto pre-decode the address information. Subsequently, the column decoderin circuit 212 and row decoder 214 are used to active the bitline andwordline corresponding to the address data. In the case of a “page read”command, multiple bitlines are activated corresponding to a wordline.Subsequently, the data stored in the memory bank 202 is transferred to apage register in circuit 212 after being sensed by sense amplifiers. Thedata in the page register may not be available until time 318 in FIG.3A, i.e. the output pin SOPx will indicate “busy”. The amount of timelapsed is referred to as the transfer time (t.sub.R). The transfer timeperiod ends at time 318 (in FIG. 3A) and lasts for a duration oft.sub.R). Before the transfer time period elapses, a memory bank statusindicator is set to indicate that the particular memory bank (e.g.,memory bank 202) is “busy”. The illustrative memory bank statusindicator of FIG. 3A is a 1-byte field with one of the bits (e.g., bit4) indicating whether memory bank 202 (i.e., bank 0) is “busy” or“ready”. The memory bank status indicator is stored in a status register288 of FIG. 2E. The memory bank status indicator is updated (e.g. bit 4is set to ‘0’) after a memory bank has been identified from the incomingdata stream. Once the memory operation is complete, the bank statusindicator is updated (e.g., bit 4 is set to ‘1’) to indicate that thememory bank is no longer “busy” (i.e., “ready”). Note that both the bankstatus indicator as well as the SOPx output pin will indicate the “busy”status as will be explained in further detail below. One of skill in theart will appreciate that although the memory bank status indicator isdepicted in FIG. 3A as a 1-byte field, its size is not necessarily solimited. At least one benefit of a larger status indicator is theability to monitor the status of a greater quantity of memory banks. Inaddition, the status indicator may be used to monitor other types ofstatus (e.g. whether the memory bank is in a “pass” or “fail” statusafter a memory operation, such as a “page program”, was performed). Inaddition, it will be apparent to one skilled in the art that the statusindicator of this example being implemented such that each bitdesignates the status of a different memory bank is exemplary only. Forexample, the value of a combination of bits may be used to indicate thestatus of a memory bank (e.g., by using logic gates and othercircuitry). The operation of the “read status” command corresponding tothe memory bank status indicator is discussed in relation to FIG. 7below.

The memory bank status indicator in the example of FIG. 3A is read usingthe “read status” memory command 316 (in step 328). Sometime during thetransfer time period, a “read status” command 316 is sent to the commandregister in the register block 224. The “read status” command instructsthe memory device 200 to monitor the status of the memory bank 202 todetermine when the transfer of data from the memory bank 202 to a pageregister 216 is complete. The “read status” command is sent from thecontrol module 238 through the data path control module 230 or directlyby the data path control module 230. Once the “read status” command hasbeen issued (e.g., sent to a command interpreter 228 and/or controlmodule 238) the output port enable (OPEX) signal 310 is driven high andthe contents of the memory bank status indicator are outputted throughthe serial output (SOPx) port 312. Similar to the IPEx signal 306, theOPEx signal 310 enables the serial output port buffer (e.g., the dataoutput register) when set to high. At time 318 in FIG. 3A, the statusindicator data in the SOPx indicates that the memory bank 202 haschanged (in step 330) from a “busy” status to a “ready” status. The OPExsignal 310 is returned to low since the content of the status indicatoris no longer needed.

Next in FIG. 3A, the IPEx signal is set high, and a “page read” command320 with no trailing address data is re-issued (in step 332) to thecommand register in the register block 224 in order to provide data fromthe data registers to the output pin SOPx. Subsequently, the OPEx signalis set high (and IPEx is returned to low), and the contents of the pageregister 216 are transferred to the SOPx 312. The output data isprovided (in step 334) through the link interface 230 out of memorydevice 200. Error correction circuitry (not shown in the figures) cancheck the output data and indicate a read error if an error is detected.Those skilled in the art will understand that the monitoring of thestatus and re-assertion of the page read command can be automaticallydone by the system. FIG. 3A is merely one example of memory deviceoperation in accordance with aspects of the invention, and the inventionis not so limited. For example, other memory commands and timingdiagrams are envisioned in accordance with various aspects of theinvention.

For example, in FIG. 4, a simplified timing diagram for the “random dataread” command following a “page read” command is illustrated. The“random data read” command enables the reading of additional data at asingle or multiple column addresses subsequent to a “page read” commandor a “random data read” command. The data stream for a “random dataread” command 402 is comprised of three bytes: command data (in thefirst byte) and column address data (in the second and third bytes). Norow address data is required since data will be read from the same rowselected in the “page read” command. A “random data read” command issuedafter a normal “page read” command has completed results in some of thedata 404 from the current page (i.e., the page read during the earliercommand) being outputted. At least one benefit to the “random data read”command is the increased efficiency with which data from the preselectedpage may be outputted since the data is already present in a pageregister of circuit 212 corresponding to the memory bank 202.

Regarding FIG. 5A, a timing diagram for the “page program” command isillustrated. Since the embodiment illustrated in FIG. 2A utilizes aserial data input and output link structure, prior to beginning toprogram a page, the program data must first be loaded into a bank pageregister. This is accomplished with the “serial data input command”. The“serial data input” command 502 is comprised of a serial data loadingperiod during which up to a page (e.g., 2,2112 bytes) of data is loadedinto the page buffer in circuit 212. After the process of loading thedata register is complete, a “page start” command 504 is issued totransfer the data from the bank register into the appropriate memorybank. Once command 504 is issued, the internal write state machineexecutes an appropriate algorithm and controls timing to program andverify the operation. Therefore, according to an embodiment of theinvention, a “page start” command is divided into two steps: serial datainput and verification. Upon successful completion of a “page program”command, the memory bank status indicator will provide a “pass” (asopposed to a “fail”) result to indicate a successful operation. In otherrespects, the timing diagram and steps involving in the example of FIG.5A are similar to those of FIG. 3A, which was previously described ingreater detail.

Moreover, FIG. 5B shows a simplified flowchart paralleling the operationof the “page program” command in the timing diagram of FIG. 5A. In step506, the “serial data input” command 502 is input to the serial inputport (SIP) line. The data stream input to the SIP line in this exampleis a multi-byte serial data stream (i.e., serial input data) beginningwith the command data (in the first byte). Next, the column address data(in the second and third bytes of the serial data stream) and rowaddress/bank data (in the fourth, fifth, and sixth bytes of the serialdata stream) are input (in step 508) to the SIP line. The, the inputdata is input (in step 510) to the SIP line in the subsequent bytes ofthe serial data stream. In step 512, a “program start” command 504 isissued. Next, to monitor the status of the operation, a “read status”command is written to the SIP line (in step 514). This results in thememory device monitoring the status bits of the memory bank statusregister. Once the status bits indicate that the memory bank is ready(in step 516) and that the memory bank indicates a “pass” (in step 518),then the “page program” memory command has been successfully performed.

In addition, the “page read for copy” and “target address input forcopy” memory commands are others operations performed by a memory devicein accordance with aspects of the invention. If the “page read for copy”command is written to the command register of the serial link interface,then the internal source address (in 3 bytes) of the memory location iswritten. Once the source address is inputted, the memory devicetransfers the contents of the memory bank at the specified sourceaddress into a data register. Subsequently, the “target address inputfor copy” memory command (with a 3-byte bank/row address sequence) isused to specify a target memory address for the page copy operation. A“page program” command may then be used to cause the internal controllogic to automatically write the page data to the target address. A“read status” command can be subsequently used to confirm the successfulexecution of the command. Other memory operations will be apparent toone skilled in the art after review of the entire disclosure herein.

Regarding FIG. 6A, a timing diagram for the “erase” (or “block erase”)command is illustrated. In addition, FIG. 6B shows a simplifiedflowchart paralleling the operation of the “erase” command in the timingdiagram of FIG. 6A. One skilled in the art is aware that erasingtypically occurs at the block level. For example, a Flash memory device200 can have, at each bank, 2,048 erasable blocks organized as 642,112-byte (2,048+64 bytes) pages per block. Each block is 132K bytes(128K+4K bytes). The “erase” command operates on one block at a time.Block erasing is started by writing command data 602 at step 610corresponding to the “erase” command (i.e., command data of ‘6011’) tothe command register via SIPx along with three bytes for row and bankaddresses at step 612. After the command and address input arecompleted, the internal erase state machine automatically executes theproperty algorithm and controls all the necessary timing to erase andverify the operation. Note that the “erase” operation may be executed bywriting or programming a logic value of ‘1’ to every memory location ina block of memory. In order to monitor the erase status to determinewhen the tBERS (i.e., block erase time) is completed, the “read status”command 604 (e.g., command data corresponding 70 h) may be issued atstep 614. After a “read status” command, all read cycles will be fromthe memory bank status register until a new command is given. In thisexample, the appropriate bit (e.g., bit 4) of the memory bank statusregister reflects the state (e.g., busy or ready) of the correspondingmemory bank. When the bank becomes ready at step 618, the appropriatebit (e.g., bit 0 of the memory bank status register is checked at step620 to determine if the erase operation passed (i.e., successfullyperformed) at step 622 or failed at step 624. In some respects, thetiming diagram and steps involving in the example of FIG. 6A are similarto those of FIG. 3A, which was previously described in greater detail.

Regarding FIG. 7, the memory bank status indicator is read using the“read status” memory command. When a “read status” command (i.e., ‘70h’) is sent at 702 to the command register 256 in FIG. 2C, the memorydevice 200 is instructed to monitor the status of the memory bank 202to, among other things, determine when the transfer of data from thememory bank 202 to the page buffer in circuit 212 is successfullycompleted. Once the “read status” command has been issued (e.g., sent toa command interpreter 262) the output port enable (OPEX) signal isdriven high and the contents of the memory bank status indicator areoutputted at 704 through the serial output (SOPx) port. The OPEx signalenables the serial output port buffer (e.g., the data output register)when set to high. In the example of FIG. 7, the memory bank statusindicator is a 1 -byte (i.e., 8-bit) field with each bit indicating,among other things, whether a memory bank (e.g., memory bank 202) is“busy” or “ready” and/or whether a operation performed on a memory bank(e.g., “erase” command) is has “passed” or “failed”. One of skill in theart will appreciate that although the memory bank status indicator isdepicted in FIG. 7 as a 1-byte field, its size is not necessarily solimited. At least one benefit of a larger status indicator is theability to monitor the status of a greater quantity of memory banks. Inaddition, it will be apparent to one skilled in the art that althoughthe status indicator of this example was implemented such that each bitdesignated the status of a different memory bank, the invention is notso limited. For example, the value of a combination of bits may be usedto indicate the status of a memory bank (e.g., by using logic gates andother circuitry).

FIGS. 8A, 8B, and 8C illustrate timing diagrams for a memory device inaccordance with aspects of the invention being used to performconcurrent operations using dual independent serial data links 230 and236. Some concurrent operations performed by a memory device inaccordance with aspects of the invention include, but are not limitedto, concurrent read, concurrent program, concurrent erase, read whileprogram, read while erase, and program while erase. FIG. 8A illustratesa concurrent “page read” operation being performed on bank A (bank 202)and bank B (bank 204). In FIG. 8A, bank A is represented as “bank 0”while bank B is represented as “bank 1”. FIG. 8B. Other concurrentoperations will become apparent to one skilled in the art upon review ofthe entire disclosure herein.

Referring to FIG. 8A, concurrent “page read” operations 802, 804directed at different memory banks in a memory device 200 are executed.In a memory device 200 with dual data link interfaces 230, 236 a “pageread” command 804 is issued through data link interface 236 (i.e., link1) while a “page read” 802 is pending through data link interface 230(i.e., link 0). Although FIG. 8A shows the “page read” on bank 0starting before the “page read” on bank 1, the two “page read”operations can begin substantially simultaneously and operateconcurrently. The outputted data 806, 808 from each of the “page read”commands is simultaneously sent through their respective data linkinterfaces. Therefore, each data link interface in memory device 200 mayaccess any of the memory banks and operate independently. At least onebenefit of this feature is greater flexibility in system design and anenhancement on device utilization (e.g. bus utilization and coreutilization).

The path of the outputted data from the memory bank to the data linkinterface in FIG. 8A is similar to that of FIG. 3A discussed earlier.For example, the outputted data from memory bank 204 flows from S/A andpage buffer 218 through path switch 206 controlled by a bank address forexample, to output parallel-to-serial register block 240, and to serialdata link interface 236 (i.e., link 1). The simultaneous data transferbetween memory banks 202 and 204 and serial data link interfaces 230,236, respectively, will occur independently of each other. As the bankaddress can control path switch 206, serial data link interface 236 canaccess bank 202 instead. The number of data link interfaces in memorydevice 200 is not limited to the number of ports or pins on memorydevice 200. Nor is the number of link interfaces in memory device 200limited by the number of memory banks in the memory device. For example,each data link interface may process a single input stream and/or asingle output stream.

Furthermore, in accordance with various aspects of the invention, FIG.8B illustrates a timing diagram of a “page read” command 810 and a “pageprogram” command 812 directed at different memory banks in a memorydevice 200 being performed concurrently. In this example, a readoperation (“page read” 810) is being performed in one of the pluralityof memory banks (e.g., memory bank 202) through serial data linkinterface 230. Meanwhile, simultaneously, a write operation (“pageprogram” 812) is being performed in another of the plurality of memorybanks (e.g. memory bank 204) through serial data link interface 236. Inaccordance with various aspects of the invention, each link in thememory device 200 may access any of the memory banks and operateindependently.

FIG. 8C is an illustrative timing diagram of a memory device 200 withtwo serial data link interfaces and two memory banks performingconcurrent memory operations. First, an “erase” command 814 directed atmemory bank 0 (bank 202) is issued from serial interface link 0 (serialdata link 230). While link 0 (serial data link 230) and memory bank 0(bank 202) are busy with the “erase” command 814, a “page program”command is received at the memory device and directed to use link 1(serial data link 236). Thus, a “page program” command 816 is performedon memory bank 0 (bank 202) from serial data link interface 1 (serialdata link 236). Meanwhile, simultaneously, a read command 818 isperformed on memory bank 1 (bank 204) by serial data interface 0 (serialdata link 230). Data is transferred between serial data link interface 0(serial data link 230) and bank 0 (bank 202) during memory command 814and between the same link interface 0 (serial data link 230) and bank 1(bank 204) during memory command 818. Therefore, in accordance withaspects of the invention, each link in the memory device 200independently accesses any of the memory banks (i.e., memory banks thatare not busy).

It will be apparent to one skilled in the art, after review of theentirety disclosed herein, that FIGS. 8A, 8B, and 8C illustrate merelysome examples of concurrent memory operations envisioned in accordancewith the invention. Other examples of concurrent operations include, butare not limited to, concurrent erase, read while program, read whileerase, program while erase, erase while program, and/or concurrentprogram. One skilled in the art will recognize that the depiction of theorder of the steps in the flowchart should not be construed to limit thesteps to only that particular order. For example, read and programcommands can be issued with or without read status commands.

FIG. 9 shows a more general description of two concurrent writeoperations between a plurality of serial link interfaces and a pluralityof memory banks in accordance with aspects of the invention. FIG. 9illustrates a method of writing data via a serial data link interface toa memory bank in accordance with an embodiment of the invention. First,in step 902 a data stream is received at a serial data link interface.The data stream contains command, address and data that will be storedin registers. Next, in step 904 a serial data link interface statusindicator corresponding to the first serial data link interface isupdated to indicate that the first serial data link interface is beingutilized. Step 904 includes changing a bit value in the status register.The update in step 904 indicates that the particular interface is beingutilized. In step 906, the data stream is parsed to extract a firstmemory bank identifier. The memory bank identifier uniquely identifies amemory bank in the memory device. The memory bank identifier may beincluded within an address field or other field of the data stream.Next, after parsing the data stream to extract a memory bank identifier,in step 908 a corresponding memory bank status indicator is updated. Theupdating occurring in steps 904 and 908 can be driven by control signalsgenerated by control circuits within status/ID register 210 for example.These control signals have been omitted from the included timingdiagrams for simplicity. Finally, in step 910 the data is routed betweenthe first serial data link and the first memory bank. It should be notedthat step 910 has been simplified in this general description, sincedata is first written to a memory bank page register and thensubsequently programmed into the memory bank.

Meanwhile, another write data operation is performed on a differentmemory bank via a different serial data link interface concurrently withthe operation 902 shown. In other words, a second memory operation isconcurrently performed using a second data stream that is routed betweena second serial data link interface and a second memory bank. First asecond data stream is received at a second one of the plurality ofserial data link interfaces in step 912. The serial data link interfacesreferred to in steps 912 and 902 are all part of the same memory device.In step 914 a serial data link interface status indicator correspondingto the second data link interface is updated to indicate that the secondserial data link interface is being utilized. Next, the second datastream is parsed to extract a second memory bank identifier in step 916.A memory bank status indicator corresponding to the second memory bankidentifier is updated to indicate that the second memory bank is beingutilized in step 918 and in step 920 data is routed between the secondserial data link interface and the second memory bank via the secondmemory bank's associated page register, as previously described inrelation to the “page program” command. In FIG. 9, once the transfer ofdata has taken place, i.e., the serial data link interface has receivedall the data to be written into the designated memory bank, the serialdata link interface indicator corresponding to each serial data linkinterface will be reset to indicate that the associated link is nowavailable, while the memory bank indicator will remain busy until allassociated data has been programmed, after which the memory bankindicator will indicate that the associated bank has become available.

FIG. 10 comprises illustrative steps that may be performed when data isread from a memory bank concurrently with the writing of data shown insteps 902 to 910 in FIG. 9 (designated as steps 1010). FIG. 10illustrates an example of some of the steps that may be performed incompleting the concurrent memory operations diagrammed in FIG. 7. Firstin step 1002, a read request for data stored in a second memory bank isreceived from a second one of the plurality of serial data linkinterfaces. In step 1004, a serial data link interface status indicatorcorresponding to the second data link interface is updated to indicatethat the second serial data link interface is being utilized. A memorybank status indicator corresponding to the second memory bank identifieris updated to indicate that the second memory bank is being utilized instep 1006. Finally, in step 1008 data is routed between the secondmemory bank and the second serial data link interface. One or more ofthe steps shown in FIG. 10 may be performed concurrently.

Returning to FIG. 1B, the memory device shown includes a single datalink interface 120 configuration that uses a virtual multiple link. FIG.1B can be implemented with the configuration of the input serial toparallel register 232 that has been previously described. Moregenerally, the embodiment of FIG. 1B can be implemented with the memorydevice 200, but with only one of the two serial data links being used.In conventional flash memory, I/O pins are occupied until an operationis complete. Therefore, no operation can be asserted during device busystatus, which reduces device availability and decreases overallperformance. In the example depicted in FIG. 1B, any available memorybank checked by “read status” operation can be accessed after anoperation has been initiated in one of the two memory banks.Subsequently, the memory device can utilize the serial data link toaccess available memory banks through the supplemental switch circuit.Therefore, in accordance with this aspect of the invention, a singlelink may be used to access multiple memory banks. This virtual multiplelink configuration emulates multiple link operations using a singlelink.

FIG. 12 illustrates a timing diagram of a memory device with two memorybanks performing memory operations using a virtual multiple linkconfigureation in which a “page program” in bank 0 and “page read” inbank 1 are to be executed. First, a “page program” command 1202 directedat memory bank 0 is issued. The “page program” command has already beendescribed earlier, but to recap, the “serial data input” command isfirst performed to load into the bank 0 page register that data to beprogrammed to bank 0. Subsequently, a “page program command is issuedand the data is written from the page register into bank 0. When a “readstatus” command 1204 is issued device, the device indicates 1206 thatbank 1 is “ready” (and that bank 0 is “busy”). Consequently, based onthe virtual multiple link configuration in accordance with theinvention, a “page read” command 1208 directed at memory bank 1 can beand is issued while memory bank 0 is busy. The “page read” command hasbeen previously described. A “read status” command 1210 can be (and inFIG. 12 is shown to be) issued to determine the status of the memorybanks. The result of the “read status” command indicates during interval1212 that both memory bank 0 and memory bank 1 are ready. Finally, a“page read” command 1214 (for bank 1) is issued that results in thecontents of the memory address corresponding to the bank 1 “page read”command to be outputted on the serial output pin (SOP). Note that whilethe “page program” operation on bank 0 is taking place, the serial datainterface link pin SIP is available to receive the “read status” commandwhich identifies bank 1 as “ready”. Similarly, once the “page read”command on bank 1 has been initialized, the SIP pin is again availablefor a “read status” command, indicating that both banks 0 and 1 are nowready. As a result, the single serial data interface link can be used toaccess and check the status of both banks. Aspects of the virtualmultiple link feature implemented in FIG. 12 illustrate that the link isavailable even while an earlier memory operation is pending. At leastone benefit arising from this feature is the reduced pin count resultingfrom the virtual multiple link configuration. Another benefit is theincreased performance of the memory device.

In addition, when aspects of the virtual multiple link feature areimplemented with memory devices with dual or quad-link configurations,it may be desirable to consider all but one of the links as beinginactive. For example, three of the four links in quad-linkconfiguration (in FIG. 1C) may not be used and may be designated as NC(no connection). At least one benefit of such an implementation is areduction in the number of pins on the memory device while maintaininglink flexibility and availability.

In accordance with various aspects of the invention, FIG. 13Aillustrates a daisy-chain cascade configuration 1300 for seriallyconnecting multiple memory devices 200. In particular, Device 0 iscomprised of a plurality of data input ports (SIP0, SIP1), a pluralityof data output ports (SOP0, SOP1), a plurality of control input ports(IPE0, IPE1), and a plurality of control output ports (OPE0, OPE1).These data and control signals are sent to the memory device 1300 froman external source (e.g., memory controller (not shown)). Moreover, inaccordance with the invention, a second flash memory device (Device 1)may be comprised of the same types of ports as Device 0. Device 1 may beserially connected to Device 0. For example, Device 1 can receive dataand control signals from Device 0. One or more additional devices mayalso be serially connected alongside Device 0 and Device 1 in a similarmanner. The final device (e.g., Device 3) in the cascade configurationprovides data and control signals back to the memory controller after apredetermined latency. Each memory device 200 (e.g., device 0, 1, 2, 3)outputs an echo (IPEQ0, IPEQ1, OPEQ0, OPEQ1) of IPE0, IPE1, OPE0, andOPE1 (i.e., control output ports) to the subsequent device. Thepreviously described circuits in FIG. 2B illustrate how the signals canbe passed from one device to a subsequent daisy chained device. Inaddition, a single clock signal is communicated to each of the pluralityof serially connected memory devices.

In the aforementioned cascade configuration, device operations of thecascaded memory device 1300 are the same as in a non-cascaded memorydevice 200. One skilled in the art will recognize that the overalllatency of the memory device 1300 may be increased in a cascadeconfiguration. For example, FIG. 14 depicts a highly-simplified timingdiagram for a “page read” memory command 1402 received at memory device1300 and directed at a memory bank in Device 2 in memory device 1300.The memory command is received at memory device 1300 and sent throughDevice 0 and Device 1 to Device 2. For example, the data streamcorresponding to the “page read” command 1402 will be transferred fromthe SIP0 line of Device 0 in memory device 1300 through the circuitry ofDevice 0 and outputted at the SOP0 line of Device 0. The output ofDevice 0 is reflected in the simplified timing diagram in FIG. 14 on theSOPx_D0 output line at 1404. “SOPx_D0” corresponds to serial output port0 on Device 0. Similarly, the data stream is subsequently received atSIPx_D1 on Device 1 (at 1406) and sent through Device 1 to be outputtedby Device 1 on the SOPx_D1 line at 1408. Next, the data stream isreceived at SIPx_D2 on Device 2 at 1410. In this example, since the“page read” command is directed to a memory bank in Device 2, in amanner similar to that described for the circuitry in memory device 200,the circuitry in Device 2 receives the “page read” command and controlsthe transfer of the requested data from a memory bank in Device 2 to theSOPx_D2 output line on Device 2 at 1412. The data outputted by Device 2is received at Device 3 at 1414 and transferred through Device 3 andoutputted from memory device 1300. One skilled in the art will recognizefrom the simplified timing diagram of FIG. 14 that a predeterminedlatency of four clock cycles resulted due to the cascadingconfiguration.

Meanwhile, the cascade configuration allows a virtually unlimited numberof devices to be connected without sacrificing device throughput.Aspects of the invention may be beneficial in the implementation ofmulti-chip package solutions and solid state mass storage applications.The incoming data stream in a cascaded device 1300 is similar to that ofa non-cascaded memory device 200, however, the first byte of the datastream may be preceded by a one-byte device identifier. For example, avalue of “0000” in the first byte may indicate Device 0, while a valueof “0001” may indicate Device 1. Once skilled in the art will understandthat the device identifier need not necessarily be limited to one byte,but may be increased or decreased as desired. Also, the deviceidentifier need not necessarily be positioned as the first byte in adata stream. For example, the size of the identifier may be increased toaccommodate more devices in a cascaded configuration and be positionedwith the address field of the data stream.

In one embodiment in accordance with the invention, the memory device200 uses a single monolithic 4 Gb chip. In another embodiment, thememory device uses a pair of stacked chips for 8 Gb. In yet anotherembodiment, the memory device 1300 uses a stack of four chips to make up16 Gb. A flash memory device in accordance with various aspects of theinvention may be an improved solution for large nonvolatile storageapplications such as solid state file storage and other portableapplications desiring non-volatility. The memory device 1300 may benefitfrom a novel flash device cascade scheme for virtually unlimited numberof linked devices to accommodate system integration with greaterexpandability and flexibility. The serial interface will provideadditional performance improvement with higher clock rate, better signalintegrity and lower power consumption. The serial interface alsoprovides unlimited expandable I/O width without changing packageconfiguration. Furthermore, the one-side pad architecture of a memorydevice in accordance with the invention, with fewer number of I/O,greatly reduces chip package size.

FIG. 13B shows another example of system implementation of deviceconnection in daisy-chain cascade configuration using a plurality of thememory devices 1500 illustrated in FIG. 15A. As described above withrespect to FIGS. 15A and 15B, the memory devices include a single serialinput port (SIP), a single serial output port (SOP), a pair of inputenable (IPE) and output enable (OPE) ports, and corresponding pair ofinput enable echo (IPEQ) and output enable echo (OPEQ) ports. In thiscascade configuration a serial clock output port (SCLKO) is added inevery device. And serial clock input port name is changed to SCLKI inorder to distinguish it from serial clock output port (SCLKO).Additional circuitry such as phase lock loop (PLL) or digital-phase lockloop (DLL) circuitry may be used in every device in order to match (orsynchronize) any phase difference between SCLKI and SCLKO signals.

Examples of some of the operations of cascaded memory devices in for aFlash 5 core architecture implementation are shown in Table 3 below.Table 3 lists the target device address (TDA), possible OP (operation)codes and corresponding states of the column address, row/bank address,and the input data.

TABLE 3 Command Set Input Target Data Device OP Column Row/Bank (1 ByteAddress Code Address Address to 2112 Operation (1 Byte) (1 Byte) (2Bytes) (3 Bytes) Bytes) Page Read tda 00h Valid Valid — Random Data Readtda 05h Valid — — Page Read for Copy tda 35h — Valid — Target Addresstda 8Fh — Valid — Input for Copy Serial Data Input tda 80h Valid ValidValid Random Data Input tda 85h Valid — Valid Page Program tda 10h — — —Block Erase tda 60h — Valid — Read Status tda 70h — — — Read ID tda 90h— — — Write Configuration tda A0h — — Valid (1 Byte) Register Write DN(Device 00h B0h — — — Name) Entry Reset tda FFh — — — Bank Select tda20h — Valid — (Bank)

In some embodiments of the present invention, each device in system 1300of FIG. 13A or in system 1310 of FIG. 13B may possess a unique deviceidentifier that may be used as a target device address (tda) in theserial input data. When receiving the serial input data, a flash memorydevice may parse the target device address field in the serial inputdata, and determine whether the device is the target device bycorrelating the target device address with the unique deviceidentification number of the device.

Table 4 shows a preferred input sequence of the input data stream inaccordance with embodiments of the present invention, including thesystems described in connection with FIGS. 13A and 13B. The commands,addresses, and data are serially shifted in and out of the memory device1500, starting with the most significant bit. Serial input signal (SIP)is sampled at the rising edges of serial clock (SCLK) while Input PortEnable (IPE) is HIGH. Command sequences start with a one-byte targetdevice address (“tda”) and one-byte operation code, also referredinterchangeably as a command code (“cmd” in Table 3). By starting theserial input signal with the one-byte target device address at the mostsignificant bit, the device may parse the target device address fieldprior to processing any additional input data received. If the memorydevice is not the target device, it may transfer the serial input datato another device prior to processing, thus saving additional processingtime and resources.

TABLE 4 Input Sequence in Byte Mode 1^(st) 2^(nd) 3^(rd) 4^(th) 5^(th)6^(th) 7^(th) 8^(th) 2116^(th) 2119^(th) Operation Byte Byte Byte ByteByte Byte Byte Byte ...Byte ...Byte Page Read tda cmd ca ca ra ra ra — —— — — Random Data Read tda cmd ca ca — — — — — — — — Page Read for Copytda cmd ra ra ra — — — — — — — Target Address Input tda cmd ra ra ra — —— — — — — for Copy Serial Data Input tda cmd ca ca ra ra ra data ...data...data Random Data Input tda cmd ca ca data data data data ...data — —Page Program tda cmd — — — — — — — — — — Block Erase tda cmd ra ra ra —— — — — — — Read Status tda cmd — — — — — — — — — — Read ID tda cmd — —— — — — — — — — Write Configuration tda cmd data — — — — — — — — —Register Write DN Entry tda cmd — — — — — — — — — — Reset tda cmd — — —— — — — — — —

The 1-byte TDA is shifted into the device, followed by the 1-byte cmbcode. The most significant bit (MSB) starts on the SIP and each bit islatched at the rising edges of serial clock (SCLK). Depending on thecommand, the one-byte command code may be followed by column addressbytes, row address bytes, bank address bytes, data bytes, and/or acombination or none.

In embodiments of the present invention, the signal bus on a flashdevice is fully multiplexed. Commands, addresses and data input/outputsmay share the same pin. As an example, the command sequence normallyconsists of one-byte target device address latch cycles, one-bytecommand latch cycles, address latch cycles (e.g. 2-bytes for columnaddresses, and 3-bytes for row addresses) and one byte or more (up to2,112 bytes) data input latch cycles if required. Every set of commandinstructions is followed by two extra clock cycles after IPE makes aHIGH to LOW transition. In the case of a daisy-chain cascadedconfiguration, the clock cycle delay after IPE transitions to LOW maydepend on the number of cascaded devices in the configuration. Inembodiments of the present invention, the serial input sequence is“byte-based”, which means that IPE and SIP should be valid for the unitof 8-clock cycles. If IPE makes a HIGH to LOW transition before thecompletion of full byte (i.e. 8 clock cycles), the corresponding commandand/or address sequences will be ignored by device. For the case of datainput sequence, the last incomplete byte of input data will be ignored,but prior complete byte(s) of input data will be valid.

FIGS. 16A, 16B, 17A, and 17B illustrate example timing diagrams relatingto the input and output latch timing of serial data at memory devices ofthe present invention.

FIG. 16A illustrates basic input latch timing consistent with theprinciples of the present invention. When receiving data at a serialinput port (SIP), TDA/Command/Address/Data-Inputs are asserted throughthe SIP port and captured on the rising edge of SCLK when CS# is LOW andIPE is HIGH. FIG. 16B is a clock diagram illustrating in detail theinput sequence in byte mode. The input data must be shifted in to thedevice, most significant bit (MSB) first on SIP, each bit being latchedat the rising edge of SCLK.

FIG. 17A illustrates basic output latch timing consistent withprinciples of the present invention. When sending data from a devicethrough serial output ports (SOP), data is asserted through SOP port onthe rising edge of SCLK when CS# is LOW and OPE is HIGH. The serial dataoutput on SOP is synchronously shifted out at the rising edge of SCLK.FIG. 17B is a clock diagram illustrating in detail the output sequencein byte mode. The output data is shifted from the device, mostsignificant bit (MSB) first on SOP, each bit being synchronized at therising edge of SCLK.

As stated earlier, the memory devices can be dual-bank memories, whereeach bank can be accessed by any serial link. Alternatively, in otherembodiments of the invention, memory devices may include a single memorybank and single serial interface. The serial interface of the memorydevice greatly improves data throughput over traditional parallelinterface schemes, while supporting feature-rich operations. Forexample, a program operation can be performed in 200 μs on a (2K+64)byte page and an erase operation can be performed in 1.5 ms on a(128K+4K) byte block. An on-clip write controller may be used toautomate all program and erase functions including pulse repetition,where used, and internal verification and margining of data. Inwrite-intensive systems, ECC (Error Correcting Code) with real timemapping-out algorithm may be used to enhance the extended reliability of100K program/erase cycles in the memory device.

The usefulness of the various aspects of the invention should beapparent to one skilled in the art. The use of any and all examples orexemplary language herein (e.g., “such as”) is intended merely to betterilluminate the invention and does not pose a limitation on the scope ofthe invention unless otherwise claimed. No language in the specificationshould be construed as indicating any non-claimed element as essentialto the practice of the invention.

The present invention has sometimes been described in terms of preferredand illustrative embodiments thereof. Numerous other embodiments,modifications and variations within the scope and spirit of the appendedclaims will occur to persons of ordinary skill in the art from a reviewof this disclosure.

What is claimed is:
 1. A system comprising: a memory device including:non-volatile memory; a clock input configured to receive a clock signal;a common command and data input configured to receive input data andcommand data at different times; a first control input configured toreceive a first of two control signals; a second control inputconfigured to receive a second of the two control signals; corecircuitry configured to execute an operation on the non-volatile memorycorresponding to the command data; and latch circuitry configured to:latch the command data while the first of the two control signals isheld at an active logic level for at least a duration of time that thecommand data is received at the common command and data input, and latchthe input data in synchronization with both rising and falling edges ofthe clock signal; and a memory controller communicatively coupled to thememory device, and the memory controller being configured to source theinput data to the memory device.
 2. The system as claimed in claim 1wherein only the first of the two control signals is held at the activelogic level for at least the duration of time that the command data isreceived at the common command and data input.
 3. The system as claimedin claim 1 wherein the first of the two control signals is an input portenable signal.
 4. The system as claimed in claim 1 wherein the second ofthe two control signals is an output port enable signal.
 5. The systemas claimed in claim 1 wherein the operation is an erase operation. 6.The system as claimed in claim 1 wherein the operation is a programoperation.
 7. The system as claimed in claim 1 wherein the commoncommand and data input is a serial input.
 8. The system as claimed inclaim 1 wherein the non-volatile memory is flash memory.
 9. The systemas claimed in claim 8 wherein the flash memory is NAND flash memory. 10.The system as claimed in claim 1 wherein a transitioning of the first ofthe two control signals from an inactive state to the active stateindicates a beginning of the command data being received at the commoncommand and data input.
 11. The system as claimed in claim 1 furthercomprising at least one additional memory device.
 12. The system asclaimed in claim 11 wherein the memory device and the at least oneadditional memory device form a plurality of serially connected memorydevices.
 13. A method carried out in a memory system that includes amemory controller and a memory device, the memory device havingnon-volatile memory, a clock input and a common command and data input,and the method comprising: sourcing input data to the memory device;receiving a clock signal at the clock input; receiving, at the commoncommand and data input and at different times, the input data andcommand data; receiving a first of two control signals; receiving asecond of the two control signals; latching the command data while thefirst of the two control signals is held at an active logic level for atleast a duration of time that the command data is received at the commoncommand and data input; latching the input data in synchronization withboth rising and falling edges of the clock signal; and executing anoperation on the non-volatile memory corresponding to the command data.14. The method as claimed in claim 13 wherein only the first of the twocontrol signals is held at the active logic level for at least theduration of time that the command data is received at the common commandand data input.
 15. The method as claimed in claim 13 wherein the firstof the two control signals is an input port enable signal.
 16. Themethod as claimed in claim 13 wherein the second of the two controlsignals is an output port enable signal.
 17. The method as claimed inclaim 13 wherein the operation is an erase operation.
 18. The method asclaimed in claim 13 wherein the operation is a program operation. 19.The method as claimed in claim 13 wherein the common command and datainput is a serial input.
 20. The method as claimed in claim 13 whereinthe non-volatile memory is flash memory.
 21. The method as claimed inclaim 20 wherein the flash memory is NAND flash memory.
 22. The methodas claimed in claim 13 wherein a transitioning of the first of the twocontrol signals from an inactive state to the active state indicates abeginning of the command data being received at the common command anddata input.